fix: return index.html for /swagger and /swagger/ instead of 404#328
Merged
sdghchj merged 3 commits intoswaggo:masterfrom Dec 20, 2025
Merged
Conversation
Contributor
Author
|
@easonlin404 @pei0804 @sdghchj Hi, just a small ping in case this PR was missed 🙂 |
Member
|
test with go 1.21.x failed. |
Contributor
Author
|
@sdghchj Could you please approve and re-run the GitHub Actions for this PR? |
sdghchj
approved these changes
Dec 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the PR
Fixes the issue where accessing /swagger and /swagger/ returned 404. Now, both paths return the content of index.html directly, matching typical static web server behavior and improving UX.
Closes #323
Additional context:
example/basic/main.goas follows to ensure Swagger UI loads the API definition correctly: